SPR

Technote

Problem:
This issue was reported to Quality Engineering as SPR# AHUR5J7LDX, and is fixed
in Notes 6.5.5 Client and Notes 7.0 Client.

Excerpt from the Lotus Notes and Lotus Domino Release 6.5.5 MR fix list
(available at http://www.ibm.com/developerworks/lotus):

Editor
SPR# AHUR5J7LDX - Fixed a problem which appears to be a hang when using the
arrow icons to scroll to a document which requires user intervention. This
problem only happens when using the scroll arrow Smarticon from within an open
document, and is not a client hang. If you use the scroll arrow Smarticon from
a view/folder, it works fine. What is happening is that somehow the messagebox
is displayed (you get the beep) but it's going in the background. Notes won't
respond because it has the message box displayed, but the message box isn't in
the front so it appears like Notes is hung. Even hitting ENTER, or Y or N will
get rid of the dialog box (it does have the focus, just isn't in the
foreground).

A workaround to this problem would be to hit the ALT key, you will see the
MessageBox displayed in the front and you can continue from then on.

Refer to the Upgrade Central site for details on upgrading Notes/Domino.

The issue occurs in cases where the document to be opened is based on a form
design that calls the LotusScript MessageBox function (or statement) in its
QueryOpen or PostOpen event, and the form design contains at least one Action.

Example of steps to reproduce:
1. From user A's mail file, send a meeting invitation to user B. Don't have
user B open the invitation.
2. Have user A reschedule the meeting created above.
3. Open user B's mail file and re-sort the Date column in the Inbox so that
new mail shows at the top.
4. Open the reschedule notice rather than the original meeting invitation.
5. Press the ENTER key to open the next document, which is the invitation
document.

or

Click the 'Next' Toolbar icon to move to the next mail message in the mail
view.

A blank white screen then appears and the CPU usage spikes to 100%.


To get Notes to respond:

Starting with the Notes 6.0.4/6.5.1 releases, pressing the CTRL+BREAK keys will
allow the client to become responsive.

With releases prior to the above, if it is critical to get Notes to respond
before ending the task through the operating system, try the following:

1. Press CTRL+BREAK.
2. Wait 15 minutes (or more)
3. Press CTRL+BREAK again.


To avoid the issue by using the user interface differently:

If your scenario matches the example of steps to reproduce above, change the
date sort order in the view. The problem will not occur with the view sorted
in Ascending order by date.

OR

Rather than navigating to the next document from an open document, close the
present document and navigate to the next document from the view level, and
then open it. Do not use the icon on the Toolbar or the ENTER key to navigate
through the Inbox.



To avoid the issue by altering the form design:

Either re-design the application so that it does not make any MessageBox calls
within the QueryOpen or PostOpen events, or remove any Actions from the form's
design. More >